Skip to content

ci: add npm provenance#415

Merged
Ujstor merged 2 commits intoMelkeydev:mainfrom
naxodev:ci/add-provenance-to-npm
Jul 19, 2025
Merged

ci: add npm provenance#415
Ujstor merged 2 commits intoMelkeydev:mainfrom
naxodev:ci/add-provenance-to-npm

Conversation

@NachoVazquez
Copy link
Contributor

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.

Problem/Feature

We are not generating NPM provenance when releasing to NPM.

https://docs.npmjs.com/generating-provenance-statements

Description of Changes:

  • We added the necessary permissions to generate the npm provenance
  • We added the --provenance flag to the npm publish command

Checklist

@Ujstor
Copy link
Collaborator

Ujstor commented Jul 19, 2025

@NachoVazquez Thanks for the PR. I need to create an NPM_TOKEN and test the release

@NachoVazquez
Copy link
Contributor Author

Yes, @Ujstor, that's the only thing pending. It can be triggered manually, so you don't need to create a new version. We will just take what's on the GitHub release matching the entered version.

@NachoVazquez
Copy link
Contributor Author

I'll be pending, so I can release v2 of GoNx, which will be powered by go-blueprint thanks to the npm package.

Copy link
Collaborator

@Ujstor Ujstor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@Ujstor Ujstor merged commit ebd54fa into Melkeydev:main Jul 19, 2025
195 checks passed
@Ujstor
Copy link
Collaborator

Ujstor commented Jul 19, 2025

@NachoVazquez can you check pipeline logs?
https://github.com/Melkeydev/go-blueprint/actions/runs/16392461847/job/46320246793

I did a manual trigger and was prompted to input the version, so I entered v0.10.11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants